Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a603c371ec9e6b5e1f722841889b734583a919610909bfd6b18d3b2674309d00

Tx prefix hash: 5df0cfb890cfd8b1a9dc5452ed3df67a992577745a88f394bc749347f8eae0c6
Tx public key: e2bb94f4617408e4750f22620c4b637e978a59cb5d861121baadc315e42c75d9
Timestamp: 1577876787 Timestamp [UCT]: 2020-01-01 11:06:27 Age [y:d:h:m:s]: 04:330:14:35:55
Block: 36295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125502 RingCT/type: yes/0
Extra: 01e2bb94f4617408e4750f22620c4b637e978a59cb5d861121baadc315e42c75d9021100000092c3a1a09f000000000000000000

1 output(s) for total of 465.307927043000 dcy

stealth address amount amount idx
00: 36b04f84ce45fd05f65d820b06d7069f529b4585eb2b4e58a72f826b8a946cf2 465.307927043000 61441 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": 36305, "vin": [ { "gen": { "height": 36295 } } ], "vout": [ { "amount": 465307927043, "target": { "key": "36b04f84ce45fd05f65d820b06d7069f529b4585eb2b4e58a72f826b8a946cf2" } } ], "extra": [ 1, 226, 187, 148, 244, 97, 116, 8, 228, 117, 15, 34, 98, 12, 75, 99, 126, 151, 138, 89, 203, 93, 134, 17, 33, 186, 173, 195, 21, 228, 44, 117, 217, 2, 17, 0, 0, 0, 146, 195, 161, 160, 159, 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