Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d4a942ac1fd8244db03d67a1fba79fd610385f2699b3bb52d3c96609e6fdb91

Tx prefix hash: 16edf83b069c1ab4080841c7c3f60097867e0645fd2c51e900952a6bcba8b9d5
Tx public key: 231deca7c9b021353e5f6c2af20d0e540644f933c744578bdd7d9744015f6d66
Timestamp: 1578725853 Timestamp [UCT]: 2020-01-11 06:57:33 Age [y:d:h:m:s]: 04:351:10:39:05
Block: 43119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1140611 RingCT/type: yes/0
Extra: 01231deca7c9b021353e5f6c2af20d0e540644f933c744578bdd7d9744015f6d660211000000084943cd9f000000000000000000

1 output(s) for total of 441.702336436000 dcy

stealth address amount amount idx
00: 6cf33fd49a6e4e614880cf4dc3335e9fe115e6319d89c01b71d266a66f94a4cc 441.702336436000 77942 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": 43129, "vin": [ { "gen": { "height": 43119 } } ], "vout": [ { "amount": 441702336436, "target": { "key": "6cf33fd49a6e4e614880cf4dc3335e9fe115e6319d89c01b71d266a66f94a4cc" } } ], "extra": [ 1, 35, 29, 236, 167, 201, 176, 33, 53, 62, 95, 108, 42, 242, 13, 14, 84, 6, 68, 249, 51, 199, 68, 87, 139, 221, 125, 151, 68, 1, 95, 109, 102, 2, 17, 0, 0, 0, 8, 73, 67, 205, 159, 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