Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f3bcde19fee7c9b7dd1ccc76043906c54dea59ec8f791de5d4d2f172a30a369

Tx prefix hash: 3aea86baa388a31a6a06b18937185b66d3f55537c43d1c7cc93f819e738b9e0c
Tx public key: 33c41aab3cae9578a03983d02aa198f5692c6ca8c3f26b88503ac8194754a3ac
Timestamp: 1712941013 Timestamp [UCT]: 2024-04-12 16:56:53 Age [y:d:h:m:s]: 01:016:05:57:16
Block: 999013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272594 RingCT/type: yes/0
Extra: 0133c41aab3cae9578a03983d02aa198f5692c6ca8c3f26b88503ac8194754a3ac02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db7959a43f4008228bb32e5dee926d94594c486ee9c030497c602ffb1928a703 0.600000000000 1459489 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": 999023, "vin": [ { "gen": { "height": 999013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db7959a43f4008228bb32e5dee926d94594c486ee9c030497c602ffb1928a703" } } ], "extra": [ 1, 51, 196, 26, 171, 60, 174, 149, 120, 160, 57, 131, 208, 42, 161, 152, 245, 105, 44, 108, 168, 195, 242, 107, 136, 80, 58, 200, 25, 71, 84, 163, 172, 2, 17, 0, 0, 0, 3, 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