Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1d271b094bfb9cf18da7c97e2481882ada77437fb52c4d024ce925c7409326f

Tx prefix hash: 973faa80f57e2bb92cd84e0e111e3404e6ac398e681f2ad12e33286dac0c9bae
Tx public key: db299db9268a59c297fb6cad35c859f259680a6d661f801dd0b3d525f7e80f1f
Timestamp: 1581904619 Timestamp [UCT]: 2020-02-17 01:56:59 Age [y:d:h:m:s]: 05:106:13:01:42
Block: 66406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1229297 RingCT/type: yes/0
Extra: 01db299db9268a59c297fb6cad35c859f259680a6d661f801dd0b3d525f7e80f1f021100000001026b59f3000000000000000000

1 output(s) for total of 369.802773912000 dcy

stealth address amount amount idx
00: c1cf7da34a024e1e2a6bafc5ae918f341a50f78339acf514a916ca88ff7dd18c 369.802773912000 122335 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": 66416, "vin": [ { "gen": { "height": 66406 } } ], "vout": [ { "amount": 369802773912, "target": { "key": "c1cf7da34a024e1e2a6bafc5ae918f341a50f78339acf514a916ca88ff7dd18c" } } ], "extra": [ 1, 219, 41, 157, 185, 38, 138, 89, 194, 151, 251, 108, 173, 53, 200, 89, 242, 89, 104, 10, 109, 102, 31, 128, 29, 208, 179, 213, 37, 247, 232, 15, 31, 2, 17, 0, 0, 0, 1, 2, 107, 89, 243, 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