Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2b42c5ab9656dda52adb0ad35fbcebf41b96dcd3cbf39607d62454247303b73

Tx prefix hash: 6455401e12f8655026cb3ddbc049a350db5bbf2ccabda5ae1f11343402f37a96
Tx public key: b05bf77fe520d0b85bb3fee07487580c8f6a2caf853e13ed0b24dbd92b045d4f
Timestamp: 1713327570 Timestamp [UCT]: 2024-04-17 04:19:30 Age [y:d:h:m:s]: 00:253:11:46:38
Block: 1002225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181458 RingCT/type: yes/0
Extra: 01b05bf77fe520d0b85bb3fee07487580c8f6a2caf853e13ed0b24dbd92b045d4f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2da5950e7cd344d45d10fff33b694aaefe9e5dc1d387d39a60ab03de626a6069 0.600000000000 1462741 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": 1002235, "vin": [ { "gen": { "height": 1002225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2da5950e7cd344d45d10fff33b694aaefe9e5dc1d387d39a60ab03de626a6069" } } ], "extra": [ 1, 176, 91, 247, 127, 229, 32, 208, 184, 91, 179, 254, 224, 116, 135, 88, 12, 143, 106, 44, 175, 133, 62, 19, 237, 11, 36, 219, 217, 43, 4, 93, 79, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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