Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 003b46b093e10f0f60e51661a1a1ec1ed2e7e1889d7c72c060eb868dd1d1670a

Tx prefix hash: b0ea02f321e4aefca3915e8041e0ea4f5cda645bd102e24c774a122d6a4cd775
Tx public key: 0af5373ca36f23f970ec2c9fedecf513dce29cd0f0ca6c6bdaf45a713b092d96
Timestamp: 1731351677 Timestamp [UCT]: 2024-11-11 19:01:17 Age [y:d:h:m:s]: 00:012:02:54:52
Block: 1151571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8674 RingCT/type: yes/0
Extra: 010af5373ca36f23f970ec2c9fedecf513dce29cd0f0ca6c6bdaf45a713b092d960211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81684c9b64404aa84dbc4bfef9cfe48fc6e5ed4d4268ee8475cc2f4ad35418d2 0.600000000000 1637128 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": 1151581, "vin": [ { "gen": { "height": 1151571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81684c9b64404aa84dbc4bfef9cfe48fc6e5ed4d4268ee8475cc2f4ad35418d2" } } ], "extra": [ 1, 10, 245, 55, 60, 163, 111, 35, 249, 112, 236, 44, 159, 237, 236, 245, 19, 220, 226, 156, 208, 240, 202, 108, 107, 218, 244, 90, 113, 59, 9, 45, 150, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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