Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 905d553371a1a8fdfefd4d307e979640c9b4c3460b87136e1e5cace68e643bb4

Tx prefix hash: ce7496b719d6aaa5e6a1bc3a3f01355c5c55a4d1ccf4614b05039bc9a5264ec1
Tx public key: 0b0d9d6b0427271481f927f6d1fce0aa1974d8aea47a527bad3cefb2e05e65af
Timestamp: 1703269175 Timestamp [UCT]: 2023-12-22 18:19:35 Age [y:d:h:m:s]: 01:134:15:56:25
Block: 918853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357372 RingCT/type: yes/0
Extra: 010b0d9d6b0427271481f927f6d1fce0aa1974d8aea47a527bad3cefb2e05e65af0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77342b34bd967bc3056eeb38e43a2f4f4cfa1428622a50a2ed380fb9317beb8d 0.600000000000 1376517 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": 918863, "vin": [ { "gen": { "height": 918853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77342b34bd967bc3056eeb38e43a2f4f4cfa1428622a50a2ed380fb9317beb8d" } } ], "extra": [ 1, 11, 13, 157, 107, 4, 39, 39, 20, 129, 249, 39, 246, 209, 252, 224, 170, 25, 116, 216, 174, 164, 122, 82, 123, 173, 60, 239, 178, 224, 94, 101, 175, 2, 17, 0, 0, 0, 5, 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