Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b837840930f89c3bc669f2ded8b09825b5b1930f40cac9155dd43c9f0cf6910a

Tx prefix hash: 5cbfdab44d8ca84aa32c9d7af009edde5b2794f1bdfa1904a0a14c2740752a24
Tx public key: e72ff2f868b95b8a16fcaa367c2972a40fd230b963ecd0f57a515cf281c5848c
Timestamp: 1587143148 Timestamp [UCT]: 2020-04-17 17:05:48 Age [y:d:h:m:s]: 04:257:00:26:15
Block: 93517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1092357 RingCT/type: yes/0
Extra: 01e72ff2f868b95b8a16fcaa367c2972a40fd230b963ecd0f57a515cf281c5848c021100001d7637fb5df4000000000000000000

1 output(s) for total of 300.704639399000 dcy

stealth address amount amount idx
00: cc3cc4d69b768f437c5fd3f3e1cd5a34ab897acb1f8131895cac536118d9c9b8 300.704639399000 166539 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": 93527, "vin": [ { "gen": { "height": 93517 } } ], "vout": [ { "amount": 300704639399, "target": { "key": "cc3cc4d69b768f437c5fd3f3e1cd5a34ab897acb1f8131895cac536118d9c9b8" } } ], "extra": [ 1, 231, 47, 242, 248, 104, 185, 91, 138, 22, 252, 170, 54, 124, 41, 114, 164, 15, 210, 48, 185, 99, 236, 208, 245, 122, 81, 92, 242, 129, 197, 132, 140, 2, 17, 0, 0, 29, 118, 55, 251, 93, 244, 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