Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c0a48b5bde95a401e06fa95fff140184fcfc7165edcde8c76e6562a65d1b768

Tx prefix hash: 53a5a94f40c2bb5ee0b7018c4b34725b6f0b7293cdc7610624da78ae5b7bac76
Tx public key: 7a7b09334e580c72fd2b823e2d692f9c8a72b5c1164bb43875ae44ec912550b7
Timestamp: 1578193389 Timestamp [UCT]: 2020-01-05 03:03:09 Age [y:d:h:m:s]: 04:360:16:57:05
Block: 38928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147009 RingCT/type: yes/0
Extra: 017a7b09334e580c72fd2b823e2d692f9c8a72b5c1164bb43875ae44ec912550b702110000000f4943cd9f000000000000000000

1 output(s) for total of 456.053953999000 dcy

stealth address amount amount idx
00: 17205947c0338d42148293340cd2c408dbda35a8fa849d4a00d627009d38f74a 456.053953999000 66738 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": 38938, "vin": [ { "gen": { "height": 38928 } } ], "vout": [ { "amount": 456053953999, "target": { "key": "17205947c0338d42148293340cd2c408dbda35a8fa849d4a00d627009d38f74a" } } ], "extra": [ 1, 122, 123, 9, 51, 78, 88, 12, 114, 253, 43, 130, 62, 45, 105, 47, 156, 138, 114, 181, 193, 22, 75, 180, 56, 117, 174, 68, 236, 145, 37, 80, 183, 2, 17, 0, 0, 0, 15, 73, 67, 205, 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