Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c79a17e19ae6749e20b61b229ce02fd6e6e7f55501b1f1e857aa6b65f1a8d5af

Tx prefix hash: f98c3a116ddb401094dda96bb5be2d42205012054a37c929336143a133e72c91
Tx public key: 0ecac1e2a3562e8134149662768d4832ea4e0e48529a386eb96609d40e6a907f
Timestamp: 1719172717 Timestamp [UCT]: 2024-06-23 19:58:37 Age [y:d:h:m:s]: 01:138:12:07:33
Block: 1050683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357540 RingCT/type: yes/0
Extra: 010ecac1e2a3562e8134149662768d4832ea4e0e48529a386eb96609d40e6a907f021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf81cdc1743c522378fcc7affb69f48bb112a5ef24b512807f31e5819d3edc4a 0.600000000000 1520858 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": 1050693, "vin": [ { "gen": { "height": 1050683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf81cdc1743c522378fcc7affb69f48bb112a5ef24b512807f31e5819d3edc4a" } } ], "extra": [ 1, 14, 202, 193, 226, 163, 86, 46, 129, 52, 20, 150, 98, 118, 141, 72, 50, 234, 78, 14, 72, 82, 154, 56, 110, 185, 102, 9, 212, 14, 106, 144, 127, 2, 17, 0, 0, 0, 2, 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