Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ad4f152da2c1fd3c87d00a0e4edf51ca447f4d3b845de83d1cfd9a499036235

Tx prefix hash: 33306757b6d289ea6023f00f0fcb0c70c0a324dbd67d3cecef9727d88cf1815c
Tx public key: f815de0635ed3047f01f3950cff0267b5d3afaa13d29d0108064a2d29323a80e
Timestamp: 1631276400 Timestamp [UCT]: 2021-09-10 12:20:00 Age [y:d:h:m:s]: 03:080:21:13:10
Block: 331008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 833169 RingCT/type: yes/0
Extra: 01f815de0635ed3047f01f3950cff0267b5d3afaa13d29d0108064a2d29323a80e021100000021f60c5d7e000000000000000000

1 output(s) for total of 49.117192296000 dcy

stealth address amount amount idx
00: 458c0f7afe73690312d1a52c92c041ff53ed1bf709d475f95bd6f9cd4ee0c06f 49.117192296000 684151 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": 331018, "vin": [ { "gen": { "height": 331008 } } ], "vout": [ { "amount": 49117192296, "target": { "key": "458c0f7afe73690312d1a52c92c041ff53ed1bf709d475f95bd6f9cd4ee0c06f" } } ], "extra": [ 1, 248, 21, 222, 6, 53, 237, 48, 71, 240, 31, 57, 80, 207, 240, 38, 123, 93, 58, 250, 161, 61, 41, 208, 16, 128, 100, 162, 210, 147, 35, 168, 14, 2, 17, 0, 0, 0, 33, 246, 12, 93, 126, 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