Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d2aa726bae0c651f8429ff8d47bf11eaf41b442a58306d0575704abe69bc107

Tx prefix hash: 484c14c9af83153e9b02caf8790e5dc9ca25221cb3b9f514713faad7284f01e8
Tx public key: 47e0aa2b46da1964e4b83f687fa077dc4c563e49e8515183fa6dc22abeaa7ff8
Timestamp: 1584633081 Timestamp [UCT]: 2020-03-19 15:51:21 Age [y:d:h:m:s]: 05:230:08:14:54
Block: 85160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1319245 RingCT/type: yes/0
Extra: 0147e0aa2b46da1964e4b83f687fa077dc4c563e49e8515183fa6dc22abeaa7ff80211000000598c5f723a000000000000000000

1 output(s) for total of 320.501709852000 dcy

stealth address amount amount idx
00: 31f76988dc071f9b171e477ff492ac61f97e208910da4ebf14151f94f766067e 320.501709852000 154132 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": 85170, "vin": [ { "gen": { "height": 85160 } } ], "vout": [ { "amount": 320501709852, "target": { "key": "31f76988dc071f9b171e477ff492ac61f97e208910da4ebf14151f94f766067e" } } ], "extra": [ 1, 71, 224, 170, 43, 70, 218, 25, 100, 228, 184, 63, 104, 127, 160, 119, 220, 76, 86, 62, 73, 232, 81, 81, 131, 250, 109, 194, 42, 190, 170, 127, 248, 2, 17, 0, 0, 0, 89, 140, 95, 114, 58, 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