Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cfd6e9996d0f798377f5a6ad159cf99fb2868e4b4905add19166acb93878440

Tx prefix hash: ad59c03b861c39fdfb1b71d44221589926d73d2618e07fceb30f145820abc21e
Tx public key: adcae60ef76f28b8483f148a1dc081f190a1b1f7ebdc9e3b14aa912a62119cc9
Timestamp: 1730653631 Timestamp [UCT]: 2024-11-03 17:07:11 Age [y:d:h:m:s]: 00:133:19:03:06
Block: 1145793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95471 RingCT/type: yes/0
Extra: 01adcae60ef76f28b8483f148a1dc081f190a1b1f7ebdc9e3b14aa912a62119cc90211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5278edd1d8fd30e80779bb25ad8cafed5f710f544e3daa33304a7bf7a191298 0.600000000000 1630306 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": 1145803, "vin": [ { "gen": { "height": 1145793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5278edd1d8fd30e80779bb25ad8cafed5f710f544e3daa33304a7bf7a191298" } } ], "extra": [ 1, 173, 202, 230, 14, 247, 111, 40, 184, 72, 63, 20, 138, 29, 192, 129, 241, 144, 161, 177, 247, 235, 220, 158, 59, 20, 170, 145, 42, 98, 17, 156, 201, 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