Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9679731e6e2660ae3df05acdaf09129604f7beb4f63cf02c660c1eeee08d7ac0

Tx prefix hash: 51b105fe6554c1f554f6f039d45d8275c0e3f519c733cc9af15b95b73e9d26fb
Tx public key: 29d33f3c75ca2142055fc7be4f30ac5bf2226ccde4af5e5bed820a2d0a6e7df3
Timestamp: 1580978747 Timestamp [UCT]: 2020-02-06 08:45:47 Age [y:d:h:m:s]: 04:362:03:54:01
Block: 59806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149980 RingCT/type: yes/0
Extra: 0129d33f3c75ca2142055fc7be4f30ac5bf2226ccde4af5e5bed820a2d0a6e7df30211000000040aca7173000000000000000000

1 output(s) for total of 388.900690247000 dcy

stealth address amount amount idx
00: 1be83ad429b5c0333314c637c6e0f94cfb2be5dd79f7eb9281a0f66bd7f9e211 388.900690247000 110322 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": 59816, "vin": [ { "gen": { "height": 59806 } } ], "vout": [ { "amount": 388900690247, "target": { "key": "1be83ad429b5c0333314c637c6e0f94cfb2be5dd79f7eb9281a0f66bd7f9e211" } } ], "extra": [ 1, 41, 211, 63, 60, 117, 202, 33, 66, 5, 95, 199, 190, 79, 48, 172, 91, 242, 34, 108, 205, 228, 175, 94, 91, 237, 130, 10, 45, 10, 110, 125, 243, 2, 17, 0, 0, 0, 4, 10, 202, 113, 115, 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