Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e938bc6b20faf31518f920de22d4eecda67aaea4b7f28230e23c89fe45ebde6b

Tx prefix hash: 2a4570513bd10970ede2ecc162c3a77d1e40964b495d3b413366d9aba5581259
Tx public key: 2ad350812325fb9b29ad76d606823870efb00555d983f7a9cb28b2df4c65a659
Timestamp: 1725013061 Timestamp [UCT]: 2024-08-30 10:17:41 Age [y:d:h:m:s]: 00:216:10:21:13
Block: 1099119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154531 RingCT/type: yes/0
Extra: 012ad350812325fb9b29ad76d606823870efb00555d983f7a9cb28b2df4c65a65902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 542f49f8fa620f1d90e0917a015e04be594adbedae024dff451e799fb2e3bbde 0.600000000000 1575046 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": 1099129, "vin": [ { "gen": { "height": 1099119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "542f49f8fa620f1d90e0917a015e04be594adbedae024dff451e799fb2e3bbde" } } ], "extra": [ 1, 42, 211, 80, 129, 35, 37, 251, 155, 41, 173, 118, 214, 6, 130, 56, 112, 239, 176, 5, 85, 217, 131, 247, 169, 203, 40, 178, 223, 76, 101, 166, 89, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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