Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d062e81326c747d4e0c73166a7997ed2b4b24c2d686c23d1bc3a5b19a2fbb27

Tx prefix hash: ec0a6463254e602ecd524bf95b0887278cc0236e6e7bdf4c581378ed62f88baf
Tx public key: e88e53d849d8a62ddecc892dca85fbf5515a92f9c9294959c04f9d8241a47b4a
Timestamp: 1704632007 Timestamp [UCT]: 2024-01-07 12:53:27 Age [y:d:h:m:s]: 01:334:03:56:46
Block: 930128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497697 RingCT/type: yes/0
Extra: 01e88e53d849d8a62ddecc892dca85fbf5515a92f9c9294959c04f9d8241a47b4a0211000000029da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f175c5f90df8073f60e2b0779021bb1d43ded94448575b207d4d2b810ffd229 0.600000000000 1388006 of 15

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": 930138, "vin": [ { "gen": { "height": 930128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f175c5f90df8073f60e2b0779021bb1d43ded94448575b207d4d2b810ffd229" } } ], "extra": [ 1, 232, 142, 83, 216, 73, 216, 166, 45, 222, 204, 137, 45, 202, 133, 251, 245, 81, 90, 146, 249, 201, 41, 73, 89, 192, 79, 157, 130, 65, 164, 123, 74, 2, 17, 0, 0, 0, 2, 157, 168, 225, 52, 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