Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d217db699290cc39a39c59f8b4cdc858f608d427fcde19ef0cff20b71d62e92

Tx prefix hash: 582870d4da42daa3c5d20bb063aaf66e417d1df711056b8a8e6c27dc2b13c104
Tx public key: 43e58a747d289d9f99ff41908acb698d259a7826429486230abbad4a91b852c2
Timestamp: 1650103014 Timestamp [UCT]: 2022-04-16 09:56:54 Age [y:d:h:m:s]: 03:009:11:07:18
Block: 481322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 787368 RingCT/type: yes/0
Extra: 0143e58a747d289d9f99ff41908acb698d259a7826429486230abbad4a91b852c202110000000375e3f0e9000000000000000000

1 output(s) for total of 15.602013186000 dcy

stealth address amount amount idx
00: 2783d897af5c1c3be7de226264d0bfe25a2b007f8e19ec3ba5205ea92d0ee4b3 15.602013186000 902565 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": 481332, "vin": [ { "gen": { "height": 481322 } } ], "vout": [ { "amount": 15602013186, "target": { "key": "2783d897af5c1c3be7de226264d0bfe25a2b007f8e19ec3ba5205ea92d0ee4b3" } } ], "extra": [ 1, 67, 229, 138, 116, 125, 40, 157, 159, 153, 255, 65, 144, 138, 203, 105, 141, 37, 154, 120, 38, 66, 148, 134, 35, 10, 187, 173, 74, 145, 184, 82, 194, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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