Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 264056f313a7cf71d1a6eb122b3185f7afcc3df378acaaa80aff2b521a52d51a

Tx prefix hash: 6a52273e0de18d768cfcff19b7b2e62c8bbb7ee40d4020220751f55ca8bba75f
Tx public key: d0f027ce60d4fc6f57bbe88b0be500f37fd4c8a7da76c737f97aaff318ff655c
Timestamp: 1744975746 Timestamp [UCT]: 2025-04-18 11:29:06 Age [y:d:h:m:s]: 00:217:11:53:51
Block: 1264113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153160 RingCT/type: yes/0
Extra: 01d0f027ce60d4fc6f57bbe88b0be500f37fd4c8a7da76c737f97aaff318ff655c0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1150b2aee264b6b83644a3a8346dc333b44260ccd723a826f58275d9bcd2f01c 0.600000000000 1751306 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": 1264123, "vin": [ { "gen": { "height": 1264113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1150b2aee264b6b83644a3a8346dc333b44260ccd723a826f58275d9bcd2f01c" } } ], "extra": [ 1, 208, 240, 39, 206, 96, 212, 252, 111, 87, 187, 232, 139, 11, 229, 0, 243, 127, 212, 200, 167, 218, 118, 199, 55, 249, 122, 175, 243, 24, 255, 101, 92, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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