Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dad98d7c59af3a396adb11df68fd6a6bad82205e41522bd566693476b00f6ba

Tx prefix hash: 8a816e572db27bb156f32f6c8443deb817cc461efb791fabc0129a3f8c0f0214
Tx public key: 373ace5496b45df800bc994c0dc16aec69f555bf49f31a54f232e47bd6d670b3
Timestamp: 1582933287 Timestamp [UCT]: 2020-02-28 23:41:27 Age [y:d:h:m:s]: 05:059:19:25:49
Block: 73682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1197094 RingCT/type: yes/0
Extra: 01373ace5496b45df800bc994c0dc16aec69f555bf49f31a54f232e47bd6d670b30211000000154ac5aa02000000000000000000

1 output(s) for total of 349.841372936000 dcy

stealth address amount amount idx
00: 63e4a944549e9b4f97d5ec9f2eedbf2f6e06abad56bf88b1e5fe9ca940dbdb27 349.841372936000 135973 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": 73692, "vin": [ { "gen": { "height": 73682 } } ], "vout": [ { "amount": 349841372936, "target": { "key": "63e4a944549e9b4f97d5ec9f2eedbf2f6e06abad56bf88b1e5fe9ca940dbdb27" } } ], "extra": [ 1, 55, 58, 206, 84, 150, 180, 93, 248, 0, 188, 153, 76, 13, 193, 106, 236, 105, 245, 85, 191, 73, 243, 26, 84, 242, 50, 228, 123, 214, 214, 112, 179, 2, 17, 0, 0, 0, 21, 74, 197, 170, 2, 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