Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cab2a78855d4114e1c1ab6529778b7199c2e93e45d6ff2ac8ade7d7a2873975

Tx prefix hash: 8cc486e4de435f6c4296401f6ba43c4d0423078a6f2f9c6b6fd74c55adb96faf
Tx public key: 40c1b11d19119161509d0d0676292cf77a6c6a1ef56c77bd212fe0b090e4d7f9
Timestamp: 1577825373 Timestamp [UCT]: 2019-12-31 20:49:33 Age [y:d:h:m:s]: 05:127:23:46:49
Block: 36005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1241252 RingCT/type: yes/0
Extra: 0140c1b11d19119161509d0d0676292cf77a6c6a1ef56c77bd212fe0b090e4d7f90211000000514ac5aa02000000000000000000

1 output(s) for total of 466.338575871000 dcy

stealth address amount amount idx
00: 60a4ea7a3a47511d6774fe23c1f2a1adf47c5ea890575cf31159b98bd2554edc 466.338575871000 60837 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": 36015, "vin": [ { "gen": { "height": 36005 } } ], "vout": [ { "amount": 466338575871, "target": { "key": "60a4ea7a3a47511d6774fe23c1f2a1adf47c5ea890575cf31159b98bd2554edc" } } ], "extra": [ 1, 64, 193, 177, 29, 25, 17, 145, 97, 80, 157, 13, 6, 118, 41, 44, 247, 122, 108, 106, 30, 245, 108, 119, 189, 33, 47, 224, 176, 144, 228, 215, 249, 2, 17, 0, 0, 0, 81, 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