Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0110a508a0968a8db4d3ca3d0018b00b5e7fcdf8ed92ac4583d91ef2dca51589

Tx prefix hash: 831109a62891cd57c46be90460c4e63c0e06e5d3fc388158bf5d7fc69130667a
Tx public key: d0d6ea8cbf7b9311f0841c0951af2442479b41e2f7f326f51eb4e18ff2ec6bec
Timestamp: 1740798267 Timestamp [UCT]: 2025-03-01 03:04:27 Age [y:d:h:m:s]: 00:331:12:51:38
Block: 1229508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234627 RingCT/type: yes/0
Extra: 01d0d6ea8cbf7b9311f0841c0951af2442479b41e2f7f326f51eb4e18ff2ec6bec021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3134244d697630476e52a35f178b36fbab8a87edc8c688014d909b78789b90de 0.600000000000 1716395 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": 1229518, "vin": [ { "gen": { "height": 1229508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3134244d697630476e52a35f178b36fbab8a87edc8c688014d909b78789b90de" } } ], "extra": [ 1, 208, 214, 234, 140, 191, 123, 147, 17, 240, 132, 28, 9, 81, 175, 36, 66, 71, 155, 65, 226, 247, 243, 38, 245, 30, 180, 225, 143, 242, 236, 107, 236, 2, 17, 0, 0, 0, 5, 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