Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2c8e459d1025f2399de255f7a55f4c11f6f689958c3bdf78dde44baedc9f55e

Tx prefix hash: d0f714207bd7ec3e134264ca5afeb8ea74e6802f65e408a5f2755c064372fc59
Tx public key: e08db6938f7c8c6e9a1f2b8e5b62f93d453069e2123556d925ea49360e85564c
Timestamp: 1695506512 Timestamp [UCT]: 2023-09-23 22:01:52 Age [y:d:h:m:s]: 01:123:13:07:21
Block: 854686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349554 RingCT/type: yes/0
Extra: 01e08db6938f7c8c6e9a1f2b8e5b62f93d453069e2123556d925ea49360e85564c021100000005faf35c9c000000000000000000

1 output(s) for total of 0.903796249000 dcy

stealth address amount amount idx
00: bf0b7df98a43f3fb29ff65fcf079852fba1ee98526e893d0dca3d59ba51f170e 0.903796249000 1308672 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": 854696, "vin": [ { "gen": { "height": 854686 } } ], "vout": [ { "amount": 903796249, "target": { "key": "bf0b7df98a43f3fb29ff65fcf079852fba1ee98526e893d0dca3d59ba51f170e" } } ], "extra": [ 1, 224, 141, 182, 147, 143, 124, 140, 110, 154, 31, 43, 142, 91, 98, 249, 61, 69, 48, 105, 226, 18, 53, 86, 217, 37, 234, 73, 54, 14, 133, 86, 76, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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