Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d5b193806b946ed355d7b409dbd4a88a514af35678d5409f59e98546c6208c5

Tx prefix hash: c191d906487576c25ba2515d04ca63223c4d2d5b66b5209a39afefbd405a6bbd
Tx public key: cc06271d065dc7ab3cfd1785f641698e1101fd7797d01dcce2f29859b2d27c32
Timestamp: 1712920788 Timestamp [UCT]: 2024-04-12 11:19:48 Age [y:d:h:m:s]: 01:205:06:19:48
Block: 998842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405377 RingCT/type: yes/0
Extra: 01cc06271d065dc7ab3cfd1785f641698e1101fd7797d01dcce2f29859b2d27c3202110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8718614cb55c6224e2648311e1a8df2a13db301487409fa26aae826550b4f8e 0.600000000000 1459308 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": 998852, "vin": [ { "gen": { "height": 998842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8718614cb55c6224e2648311e1a8df2a13db301487409fa26aae826550b4f8e" } } ], "extra": [ 1, 204, 6, 39, 29, 6, 93, 199, 171, 60, 253, 23, 133, 246, 65, 105, 142, 17, 1, 253, 119, 151, 208, 29, 204, 226, 242, 152, 89, 178, 210, 124, 50, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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