Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e67aeb95ec6d262384f733e387b733cb8faed12217aa831579469d0cafdd3e8

Tx prefix hash: 451f57443957e4f072082cb8ee4aa7c988dd9a769733612b6079ef9f6e27370f
Tx public key: 758558c0988349dc8867fdcf21f84c87d5fb79638078a9e4575ae66c8246a241
Timestamp: 1713978081 Timestamp [UCT]: 2024-04-24 17:01:21 Age [y:d:h:m:s]: 01:189:19:34:03
Block: 1007632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394301 RingCT/type: yes/0
Extra: 01758558c0988349dc8867fdcf21f84c87d5fb79638078a9e4575ae66c8246a24102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d1fdee595da9c8c1fc5a69e8afcf378770b6b099da0fa56596f97bddb1a8be7 0.600000000000 1469038 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": 1007642, "vin": [ { "gen": { "height": 1007632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d1fdee595da9c8c1fc5a69e8afcf378770b6b099da0fa56596f97bddb1a8be7" } } ], "extra": [ 1, 117, 133, 88, 192, 152, 131, 73, 220, 136, 103, 253, 207, 33, 248, 76, 135, 213, 251, 121, 99, 128, 120, 169, 228, 87, 90, 230, 108, 130, 70, 162, 65, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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