Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d73f5ca66445c88c1c72c6d7ea2a805306812b100fcd44bca84ab298ca36b73f

Tx prefix hash: a995fd1a7687bf4095f7b2345d3ffc90b25fa55184d76737eb2ee5b6b399a280
Tx public key: 0919ef6278ef82b717490cffd63251fa8bd754821688c96c6429c5ad8bd3228c
Timestamp: 1583075461 Timestamp [UCT]: 2020-03-01 15:11:01 Age [y:d:h:m:s]: 04:344:08:32:58
Block: 74499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1139912 RingCT/type: yes/0
Extra: 010919ef6278ef82b717490cffd63251fa8bd754821688c96c6429c5ad8bd3228c021100000001c71d3ff9000000000000000000

1 output(s) for total of 347.680427313000 dcy

stealth address amount amount idx
00: 56055cd6d0f5ea7a930cc9bf6a1f43b54562f2e7334eb738d4f89efadab73bfa 347.680427313000 137868 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": 74509, "vin": [ { "gen": { "height": 74499 } } ], "vout": [ { "amount": 347680427313, "target": { "key": "56055cd6d0f5ea7a930cc9bf6a1f43b54562f2e7334eb738d4f89efadab73bfa" } } ], "extra": [ 1, 9, 25, 239, 98, 120, 239, 130, 183, 23, 73, 12, 255, 214, 50, 81, 250, 139, 215, 84, 130, 22, 136, 201, 108, 100, 41, 197, 173, 139, 211, 34, 140, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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