Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a4c9441ea1c742044775f3ff2677993ca238cbbfd1096b60984c65c470caf11

Tx prefix hash: 6d6e32670160457eaf12e2ff0f3fc7d008011c693eb066c2f49decc6cc74fef1
Tx public key: 5a9be1d9d51292da337d2cd9ebf78ab7c2cc992bf47cab6e4d69e351db4c7763
Timestamp: 1634709671 Timestamp [UCT]: 2021-10-20 06:01:11 Age [y:d:h:m:s]: 03:069:14:23:59
Block: 356665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 827858 RingCT/type: yes/0
Extra: 015a9be1d9d51292da337d2cd9ebf78ab7c2cc992bf47cab6e4d69e351db4c776302110000004636fe6557000000000000000000

1 output(s) for total of 40.385104421000 dcy

stealth address amount amount idx
00: 8742980e26132a1941ca4fb35b2fc277f627917889b1c861421eac75b572eefa 40.385104421000 727611 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": 356675, "vin": [ { "gen": { "height": 356665 } } ], "vout": [ { "amount": 40385104421, "target": { "key": "8742980e26132a1941ca4fb35b2fc277f627917889b1c861421eac75b572eefa" } } ], "extra": [ 1, 90, 155, 225, 217, 213, 18, 146, 218, 51, 125, 44, 217, 235, 247, 138, 183, 194, 204, 153, 43, 244, 124, 171, 110, 77, 105, 227, 81, 219, 76, 119, 99, 2, 17, 0, 0, 0, 70, 54, 254, 101, 87, 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