Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87ce998615666b42fde69a378d1836a5abc649bf6797dbcaf3208f7517672da1

Tx prefix hash: 554469b1ba30f2347c3bfaeeb9a195f68b700aee5a31d7447d3a819fb1f7e03f
Tx public key: 0081a31f69efa4dc76e0bf4c8cc90211bf6dff5ad8db25c4eef9231d765871e4
Timestamp: 1728577606 Timestamp [UCT]: 2024-10-10 16:26:46 Age [y:d:h:m:s]: 00:166:22:34:51
Block: 1128670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119071 RingCT/type: yes/0
Extra: 010081a31f69efa4dc76e0bf4c8cc90211bf6dff5ad8db25c4eef9231d765871e402110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6a4e1f5bfd8e047d00b38abfa9e950eb868a0aaad0d260f9510a65074f30295 0.600000000000 1611489 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": 1128680, "vin": [ { "gen": { "height": 1128670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6a4e1f5bfd8e047d00b38abfa9e950eb868a0aaad0d260f9510a65074f30295" } } ], "extra": [ 1, 0, 129, 163, 31, 105, 239, 164, 220, 118, 224, 191, 76, 140, 201, 2, 17, 191, 109, 255, 90, 216, 219, 37, 196, 238, 249, 35, 29, 118, 88, 113, 228, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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