Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcdf927dc3cb8a22927476fe910c9a9fa09c8c517ba6cfb344f0fd714d52f30d

Tx prefix hash: f60d7223307e659be85ac66588cb9d432339d2a928b5c6e3076dbe5a13f0ebb5
Tx public key: aec8f6e131af590a5e6f87ce12fd4230b260517566f5041a6d248017f84348f7
Timestamp: 1581091119 Timestamp [UCT]: 2020-02-07 15:58:39 Age [y:d:h:m:s]: 05:027:03:12:49
Block: 60705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1171448 RingCT/type: yes/0
Extra: 01aec8f6e131af590a5e6f87ce12fd4230b260517566f5041a6d248017f84348f70211000000010aca7173000000000000000000

1 output(s) for total of 386.242404844000 dcy

stealth address amount amount idx
00: 228a08591e85778aef23f9bc403993f97ad96f2d4c6176bbe0bbc1a2441bb762 386.242404844000 111757 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": 60715, "vin": [ { "gen": { "height": 60705 } } ], "vout": [ { "amount": 386242404844, "target": { "key": "228a08591e85778aef23f9bc403993f97ad96f2d4c6176bbe0bbc1a2441bb762" } } ], "extra": [ 1, 174, 200, 246, 225, 49, 175, 89, 10, 94, 111, 135, 206, 18, 253, 66, 48, 178, 96, 81, 117, 102, 245, 4, 26, 109, 36, 128, 23, 248, 67, 72, 247, 2, 17, 0, 0, 0, 1, 10, 202, 113, 115, 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