Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 533d7c496216d3ef1c82f57aaac8f04e1535aa700a4405132bf540f725dfb759

Tx prefix hash: 791071afdc3656f8922fafbb36bcfe32ee8aa76491d81c59091085b538054f97
Tx public key: c4a97ef289e78a9fe9492165f884cabb4c479ce133e2ce820a00f281b7888a6e
Timestamp: 1719077358 Timestamp [UCT]: 2024-06-22 17:29:18 Age [y:d:h:m:s]: 01:200:02:45:41
Block: 1049891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401679 RingCT/type: yes/0
Extra: 01c4a97ef289e78a9fe9492165f884cabb4c479ce133e2ce820a00f281b7888a6e021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53f71187bc0d319e8f19a9ee49f38b1ef822ae4ccaf7f876b91b8e3a5dfbad6e 0.600000000000 1519996 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": 1049901, "vin": [ { "gen": { "height": 1049891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53f71187bc0d319e8f19a9ee49f38b1ef822ae4ccaf7f876b91b8e3a5dfbad6e" } } ], "extra": [ 1, 196, 169, 126, 242, 137, 231, 138, 159, 233, 73, 33, 101, 248, 132, 202, 187, 76, 71, 156, 225, 51, 226, 206, 130, 10, 0, 242, 129, 183, 136, 138, 110, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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