Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd81200fa04efe090c28bd8e4e4039ba554e43e0aa294d92a5623e5f854384a8

Tx prefix hash: 783e499bb047dadfe58e6a562f3f399c221c03368c77c020ba1b96f26e2e7e0a
Tx public key: b0fb5e10f19649f239c6044aa169aa4304cafacf7f62b9c54f10f585cb024e2a
Timestamp: 1732863150 Timestamp [UCT]: 2024-11-29 06:52:30 Age [y:d:h:m:s]: 00:149:20:33:31
Block: 1164104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106924 RingCT/type: yes/0
Extra: 01b0fb5e10f19649f239c6044aa169aa4304cafacf7f62b9c54f10f585cb024e2a0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd1f9170a63f79c30b1229ace5058067a122c06d50e3ef9ec947d805db5f9825 0.600000000000 1649777 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": 1164114, "vin": [ { "gen": { "height": 1164104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd1f9170a63f79c30b1229ace5058067a122c06d50e3ef9ec947d805db5f9825" } } ], "extra": [ 1, 176, 251, 94, 16, 241, 150, 73, 242, 57, 198, 4, 74, 161, 105, 170, 67, 4, 202, 250, 207, 127, 98, 185, 197, 79, 16, 245, 133, 203, 2, 78, 42, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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