Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4e8d883dbfc5f43a2aeb5c2a2e7d42e127d669785da36741d0f285327f56954c

Tx prefix hash: f10ee88cc84f647119455889deb540f97307cbcc3f815f43f5e16a9003e1f394
Tx public key: 76d475ddaea9e8f537fee707957c6aa0f4703832eb4a7834d4f83762a34415fe
Timestamp: 1704753763 Timestamp [UCT]: 2024-01-08 22:42:43 Age [y:d:h:m:s]: 01:166:01:52:28
Block: 931135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379656 RingCT/type: yes/0
Extra: 0176d475ddaea9e8f537fee707957c6aa0f4703832eb4a7834d4f83762a34415fe02110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6ddd8b9d1e659e4c11ae7191923a11db464990bdd3e40abc774575d2ca6bcb6 0.600000000000 1389027 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 931145, "vin": [ { "gen": { "height": 931135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6ddd8b9d1e659e4c11ae7191923a11db464990bdd3e40abc774575d2ca6bcb6" } } ], "extra": [ 1, 118, 212, 117, 221, 174, 169, 232, 245, 55, 254, 231, 7, 149, 124, 106, 160, 244, 112, 56, 50, 235, 74, 120, 52, 212, 248, 55, 98, 163, 68, 21, 254, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8