Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 194e1187e7410aca3a70ee132a3cfcd678cddda156c542e78b9332e01b2452a2

Tx prefix hash: b921c0f5e0c2a646492c7cbada9b650ac58628bcc1772950dd02e91445ae3d39
Tx public key: d1c32966f28df307e7223c9c35f71160b7e8a8fdccf27db8c762d8b62dfe417b
Timestamp: 1708443313 Timestamp [UCT]: 2024-02-20 15:35:13 Age [y:d:h:m:s]: 01:036:22:14:10
Block: 961744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287412 RingCT/type: yes/0
Extra: 01d1c32966f28df307e7223c9c35f71160b7e8a8fdccf27db8c762d8b62dfe417b0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49539e0e87df4651b01a4caa389631235133613cb22ab5ac8ee63c66d1077cbd 0.600000000000 1421355 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": 961754, "vin": [ { "gen": { "height": 961744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49539e0e87df4651b01a4caa389631235133613cb22ab5ac8ee63c66d1077cbd" } } ], "extra": [ 1, 209, 195, 41, 102, 242, 141, 243, 7, 231, 34, 60, 156, 53, 247, 17, 96, 183, 232, 168, 253, 204, 242, 125, 184, 199, 98, 216, 182, 45, 254, 65, 123, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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