Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4716fe6351615c6b2a2ae65ce6509a1849d5de235062668aa7eb44db8cbc57a1

Tx prefix hash: 1693fda94eb3b056f2228ffc13ac720bcb97f4f69eb95583566bbc2a538237b1
Tx public key: 4d6b87ebe94c9ee723919bd5d7bfc6d0ebe15a2a2154266daa8fd8f90802022f
Timestamp: 1674250845 Timestamp [UCT]: 2023-01-20 21:40:45 Age [y:d:h:m:s]: 01:291:05:09:29
Block: 679145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469087 RingCT/type: yes/0
Extra: 014d6b87ebe94c9ee723919bd5d7bfc6d0ebe15a2a2154266daa8fd8f90802022f02110000000274b6d784000000000000000000

1 output(s) for total of 3.449138488000 dcy

stealth address amount amount idx
00: 86617664d1c352b28081be9e47cf44bf416d7b46564f4e1506b5f9d0d35c7312 3.449138488000 1121110 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": 679155, "vin": [ { "gen": { "height": 679145 } } ], "vout": [ { "amount": 3449138488, "target": { "key": "86617664d1c352b28081be9e47cf44bf416d7b46564f4e1506b5f9d0d35c7312" } } ], "extra": [ 1, 77, 107, 135, 235, 233, 76, 158, 231, 35, 145, 155, 213, 215, 191, 198, 208, 235, 225, 90, 42, 33, 84, 38, 109, 170, 143, 216, 249, 8, 2, 2, 47, 2, 17, 0, 0, 0, 2, 116, 182, 215, 132, 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