Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2909f3758a0802bf97b874d45237ea2bc8c647074aa1d9d47ead62dedcf6b2d

Tx prefix hash: 9ec662552cbe8a2207b312c2a378d4e58ed575e62320b81d5ed586d9a94ca8aa
Tx public key: a3ddd17b734e82d532ac3cba99f8b635065597502a912ee72f8c6e948a75d686
Timestamp: 1721535577 Timestamp [UCT]: 2024-07-21 04:19:37 Age [y:d:h:m:s]: 00:172:23:49:32
Block: 1070283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123774 RingCT/type: yes/0
Extra: 01a3ddd17b734e82d532ac3cba99f8b635065597502a912ee72f8c6e948a75d6860211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0643c9d37024ff5b4f6cbd9d7198fb4eab707810bd13143c0496a6a3c6ff4cea 0.600000000000 1542052 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": 1070293, "vin": [ { "gen": { "height": 1070283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0643c9d37024ff5b4f6cbd9d7198fb4eab707810bd13143c0496a6a3c6ff4cea" } } ], "extra": [ 1, 163, 221, 209, 123, 115, 78, 130, 213, 50, 172, 60, 186, 153, 248, 182, 53, 6, 85, 151, 80, 42, 145, 46, 231, 47, 140, 110, 148, 138, 117, 214, 134, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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