Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e62d6ba8788e5a91ed362ee69df621bc70151d2c6aa6bb7b0cc198dd31366620

Tx prefix hash: 5d9594997e191df70b9d9961d1b1130f5d6f593bc94114b0eed0f343d70fa71d
Tx public key: 196ac4192240e51d9bcb7a3838172718e5cd807ce978753e211691213d3229ac
Timestamp: 1577715334 Timestamp [UCT]: 2019-12-30 14:15:34 Age [y:d:h:m:s]: 04:335:05:57:31
Block: 35081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128696 RingCT/type: yes/0
Extra: 01196ac4192240e51d9bcb7a3838172718e5cd807ce978753e211691213d3229ac0211000000018a2ee0d9000000000000000000

1 output(s) for total of 469.637685456000 dcy

stealth address amount amount idx
00: b8236f08f906f6b7c68170678a94c844991bbfa41c62926b8859866d661f9a9d 469.637685456000 59098 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": 35091, "vin": [ { "gen": { "height": 35081 } } ], "vout": [ { "amount": 469637685456, "target": { "key": "b8236f08f906f6b7c68170678a94c844991bbfa41c62926b8859866d661f9a9d" } } ], "extra": [ 1, 25, 106, 196, 25, 34, 64, 229, 29, 155, 203, 122, 56, 56, 23, 39, 24, 229, 205, 128, 124, 233, 120, 117, 62, 33, 22, 145, 33, 61, 50, 41, 172, 2, 17, 0, 0, 0, 1, 138, 46, 224, 217, 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