Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d90802eb27fadf6658ef3af841882b7a86aed3d1460ee89eca216196a5674cd2

Tx prefix hash: 45879c604706b300e8fe2f4503413e176efef6864a4c2a9d3060df7aa12ffb5f
Tx public key: a7fd53bc5828cc0d15847e598580d2158d02dee54c558be39765df5f66aa2a34
Timestamp: 1577209871 Timestamp [UCT]: 2019-12-24 17:51:11 Age [y:d:h:m:s]: 04:330:01:18:11
Block: 30948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124930 RingCT/type: yes/0
Extra: 01a7fd53bc5828cc0d15847e598580d2158d02dee54c558be39765df5f66aa2a340211000000094ac5aa02000000000000000000

1 output(s) for total of 484.701454700000 dcy

stealth address amount amount idx
00: d590cf0800468cfdbfddd611c419499f1dd6a4ab44ec1ade7a4b137c62c90e1c 484.701454700000 51086 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": 30958, "vin": [ { "gen": { "height": 30948 } } ], "vout": [ { "amount": 484701454700, "target": { "key": "d590cf0800468cfdbfddd611c419499f1dd6a4ab44ec1ade7a4b137c62c90e1c" } } ], "extra": [ 1, 167, 253, 83, 188, 88, 40, 204, 13, 21, 132, 126, 89, 133, 128, 210, 21, 141, 2, 222, 229, 76, 85, 139, 227, 151, 101, 223, 95, 102, 170, 42, 52, 2, 17, 0, 0, 0, 9, 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