Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 302eb0350347e4ef3532db9f82f82a47b28a063a09057e1ab8d8faab6fcd2175

Tx prefix hash: 3d0784ddcf4f75069117faaad4908568543066d115a6ccdc7d74180a01ff7934
Tx public key: 7f5717b9c4cd9c0186ba1bbb90ba1a3ad57a7519116deffecf91a31d7f47498f
Timestamp: 1701166109 Timestamp [UCT]: 2023-11-28 10:08:29 Age [y:d:h:m:s]: 01:135:11:06:44
Block: 901406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357993 RingCT/type: yes/0
Extra: 017f5717b9c4cd9c0186ba1bbb90ba1a3ad57a7519116deffecf91a31d7f47498f02110000000975e3f0e9000000000000000000

1 output(s) for total of 0.632801809000 dcy

stealth address amount amount idx
00: b151bcecc152f307e4a3fa37a35fcaebef3e7e600ade2d1e6fa5df8e79b17b63 0.632801809000 1357967 of 0

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": 901416, "vin": [ { "gen": { "height": 901406 } } ], "vout": [ { "amount": 632801809, "target": { "key": "b151bcecc152f307e4a3fa37a35fcaebef3e7e600ade2d1e6fa5df8e79b17b63" } } ], "extra": [ 1, 127, 87, 23, 185, 196, 205, 156, 1, 134, 186, 27, 187, 144, 186, 26, 58, 213, 122, 117, 25, 17, 109, 239, 254, 207, 145, 163, 29, 127, 71, 73, 143, 2, 17, 0, 0, 0, 9, 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