Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f286ee17416e3cd3a75c6e87c16e7eee63179943723d702bef1bca06d3628dfb

Tx prefix hash: 9a918a08563075b81a8cc71d8308e17de5953a63591e1d42f74986eb4a6e8ae6
Tx public key: 3eb53616c54ce854d8b76da621666563be23c94de8cd35f9f7c2ad9387a6cae8
Timestamp: 1685603167 Timestamp [UCT]: 2023-06-01 07:06:07 Age [y:d:h:m:s]: 01:320:20:13:36
Block: 772640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490510 RingCT/type: yes/0
Extra: 013eb53616c54ce854d8b76da621666563be23c94de8cd35f9f7c2ad9387a6cae802110000000275e3f0e9000000000000000000

1 output(s) for total of 1.690141680000 dcy

stealth address amount amount idx
00: 9f39d160f50e6e653d81812872e60dbfe4481d10f3c46892833bc6d040f0428e 1.690141680000 1222059 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": 772650, "vin": [ { "gen": { "height": 772640 } } ], "vout": [ { "amount": 1690141680, "target": { "key": "9f39d160f50e6e653d81812872e60dbfe4481d10f3c46892833bc6d040f0428e" } } ], "extra": [ 1, 62, 181, 54, 22, 197, 76, 232, 84, 216, 183, 109, 166, 33, 102, 101, 99, 190, 35, 201, 77, 232, 205, 53, 249, 247, 194, 173, 147, 135, 166, 202, 232, 2, 17, 0, 0, 0, 2, 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