Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6a5c91862142ab7c820f96276e0cfccc68845c780fae142c64b4d88fb463ead

Tx prefix hash: d481b69aa9aa7d3f453facd5783b607bce005c9160325245b5ce22e72f5b7421
Tx public key: 3eba538f733bc6c4a626062eb9c9f9895df351981ac6e592b039c621994fdfbd
Timestamp: 1737984268 Timestamp [UCT]: 2025-01-27 13:24:28 Age [y:d:h:m:s]: 00:045:23:11:36
Block: 1206253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32879 RingCT/type: yes/0
Extra: 013eba538f733bc6c4a626062eb9c9f9895df351981ac6e592b039c621994fdfbd021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b8f79af1e79a44ead8e9abfbe51829eadaba4524fd2e9f81daefc0a9cb8cd31 0.600000000000 1692956 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": 1206263, "vin": [ { "gen": { "height": 1206253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b8f79af1e79a44ead8e9abfbe51829eadaba4524fd2e9f81daefc0a9cb8cd31" } } ], "extra": [ 1, 62, 186, 83, 143, 115, 59, 198, 196, 166, 38, 6, 46, 185, 201, 249, 137, 93, 243, 81, 152, 26, 198, 229, 146, 176, 57, 198, 33, 153, 79, 223, 189, 2, 17, 0, 0, 0, 4, 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