Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b4a13579be5f64c4075a66ebdf8e3105d18f262e4e5317997514614c904a5b3

Tx prefix hash: 82b8f284c2fe985e51f08f3a4033142889dcfe53f484ac01820d77c880afc4ee
Tx public key: ede93e9f919cb6c763f91eac364a9270c367c82220994ed342aa4b56d4cd582e
Timestamp: 1578445020 Timestamp [UCT]: 2020-01-08 00:57:00 Age [y:d:h:m:s]: 04:356:11:54:25
Block: 40889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1144128 RingCT/type: yes/0
Extra: 01ede93e9f919cb6c763f91eac364a9270c367c82220994ed342aa4b56d4cd582e02110000000b4ac5aa02000000000000000000

1 output(s) for total of 449.281582161000 dcy

stealth address amount amount idx
00: 5b3b0dc0f8ae08114378b2cc9a9aa6edc2a7118001b2f31db602d856f0263b46 449.281582161000 72292 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": 40899, "vin": [ { "gen": { "height": 40889 } } ], "vout": [ { "amount": 449281582161, "target": { "key": "5b3b0dc0f8ae08114378b2cc9a9aa6edc2a7118001b2f31db602d856f0263b46" } } ], "extra": [ 1, 237, 233, 62, 159, 145, 156, 182, 199, 99, 249, 30, 172, 54, 74, 146, 112, 195, 103, 200, 34, 32, 153, 78, 211, 66, 170, 75, 86, 212, 205, 88, 46, 2, 17, 0, 0, 0, 11, 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