Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fbbae664329bb1a3bbe0e1a006c9bea1de0b1154833bb932f64017b4b934db9

Tx prefix hash: bbbf032c02bf1e587ced8441b24dde9d6b64c65203a0e2ad685ecf28d26bc6b0
Tx public key: 6afdeabae3a166b343eabab5ed1da184c9f836b2cdb91748f15672d613f49e30
Timestamp: 1732040161 Timestamp [UCT]: 2024-11-19 18:16:01 Age [y:d:h:m:s]: 00:175:12:35:47
Block: 1157287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125292 RingCT/type: yes/0
Extra: 016afdeabae3a166b343eabab5ed1da184c9f836b2cdb91748f15672d613f49e30021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a03f0e1df7ab2b3685635a47243ac6b6dc4fa8b4f503649db1464994132e4cff 0.600000000000 1642910 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": 1157297, "vin": [ { "gen": { "height": 1157287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a03f0e1df7ab2b3685635a47243ac6b6dc4fa8b4f503649db1464994132e4cff" } } ], "extra": [ 1, 106, 253, 234, 186, 227, 161, 102, 179, 67, 234, 186, 181, 237, 29, 161, 132, 201, 248, 54, 178, 205, 185, 23, 72, 241, 86, 114, 214, 19, 244, 158, 48, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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