Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 516cedd834ccb243cfb297a2ecc033948cf5bd4974c32d0e27e18c79455773be

Tx prefix hash: c6951fbbd5acee5e8e27a91cd557dc08c8e17028e0f37bc468ca49c27a794c4c
Tx public key: 052a9f44ea93d9a659f0e88a8fc4e990e088dc29e94eb99831f67c507e79d782
Timestamp: 1731331614 Timestamp [UCT]: 2024-11-11 13:26:54 Age [y:d:h:m:s]: 00:166:15:47:05
Block: 1151395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118963 RingCT/type: yes/0
Extra: 01052a9f44ea93d9a659f0e88a8fc4e990e088dc29e94eb99831f67c507e79d782021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2d71ad60a3f9109f39c6db3237d6f62cba126a7e6a76692ac1f0848426e7405 0.600000000000 1636918 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": 1151405, "vin": [ { "gen": { "height": 1151395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2d71ad60a3f9109f39c6db3237d6f62cba126a7e6a76692ac1f0848426e7405" } } ], "extra": [ 1, 5, 42, 159, 68, 234, 147, 217, 166, 89, 240, 232, 138, 143, 196, 233, 144, 224, 136, 220, 41, 233, 78, 185, 152, 49, 246, 124, 80, 126, 121, 215, 130, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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