Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5416cfe5b032f8b3a2733e6913b81290cdb6e84a126d061f06a235600d5eedd9

Tx prefix hash: bdb3e233c1cb092ae3e95d6755bcfe67c8100a0e5825c0ecf1dc1aaf127a8f51
Tx public key: 901d012282917675779f1565b8f7a6863928fc77fa8bb0a127fd798a87f4b2b8
Timestamp: 1730663706 Timestamp [UCT]: 2024-11-03 19:55:06 Age [y:d:h:m:s]: 00:170:08:04:10
Block: 1145881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121569 RingCT/type: yes/0
Extra: 01901d012282917675779f1565b8f7a6863928fc77fa8bb0a127fd798a87f4b2b80211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63cff8d032d7fba40e3a2515b54526061fb615c80b659c04f134407e8fc1477a 0.600000000000 1630408 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": 1145891, "vin": [ { "gen": { "height": 1145881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63cff8d032d7fba40e3a2515b54526061fb615c80b659c04f134407e8fc1477a" } } ], "extra": [ 1, 144, 29, 1, 34, 130, 145, 118, 117, 119, 159, 21, 101, 184, 247, 166, 134, 57, 40, 252, 119, 250, 139, 176, 161, 39, 253, 121, 138, 135, 244, 178, 184, 2, 17, 0, 0, 0, 1, 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