Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53c0ed30bd0a9401a88a208ab2d17711ea821a6be929899d0815ed1a51c699f4

Tx prefix hash: 29016223133ce06583a2dd95fbe4d97f85107d4a33d9f8a48a1a900c8bf6d7a5
Tx public key: cf796b70d83d9eebd32adb2ad1dc754ba8a191a094fb3c83eaa8676178e616c1
Timestamp: 1702687471 Timestamp [UCT]: 2023-12-16 00:44:31 Age [y:d:h:m:s]: 01:149:12:25:50
Block: 914021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368015 RingCT/type: yes/0
Extra: 01cf796b70d83d9eebd32adb2ad1dc754ba8a191a094fb3c83eaa8676178e616c102110000000775e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f0577325054ad2d9f05154bd3e9a3000940f8059c19b831c8da5b1ebbac92e8 0.600000000000 1371303 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": 914031, "vin": [ { "gen": { "height": 914021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f0577325054ad2d9f05154bd3e9a3000940f8059c19b831c8da5b1ebbac92e8" } } ], "extra": [ 1, 207, 121, 107, 112, 216, 61, 158, 235, 211, 42, 219, 42, 209, 220, 117, 75, 168, 161, 145, 160, 148, 251, 60, 131, 234, 168, 103, 97, 120, 230, 22, 193, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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