Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 416a63e008c48fc32f415043578f76f7cd0a21ab7711883608465d7fc76730f4

Tx prefix hash: ba31a0333a6514251a4b4a82e4171b6ed419f328c6e9ffcef062c23a02aaaf4a
Tx public key: 5f183437df3928a80ed892346b847886392127dc9cc089b1e87014a2e6ddd0a4
Timestamp: 1719076814 Timestamp [UCT]: 2024-06-22 17:20:14 Age [y:d:h:m:s]: 00:288:15:06:35
Block: 1049886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206254 RingCT/type: yes/0
Extra: 015f183437df3928a80ed892346b847886392127dc9cc089b1e87014a2e6ddd0a402110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 674f9cfcd8c7cd2316864d0bfbd0c6c9fdd11628d1b72331bc6541038401fae2 0.600000000000 1519991 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": 1049896, "vin": [ { "gen": { "height": 1049886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "674f9cfcd8c7cd2316864d0bfbd0c6c9fdd11628d1b72331bc6541038401fae2" } } ], "extra": [ 1, 95, 24, 52, 55, 223, 57, 40, 168, 14, 216, 146, 52, 107, 132, 120, 134, 57, 33, 39, 220, 156, 192, 137, 177, 232, 112, 20, 162, 230, 221, 208, 164, 2, 17, 0, 0, 0, 5, 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