Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f4679e4a42f313142201725e143b0d1fa9485c9b9983dc84b3dce9e151c77b1

Tx prefix hash: a5b20092574b64e463a0856f7fe952562641688a297c4239f3f444aef4e615d6
Tx public key: d0c06838c8048ff4f0679b6beaeb097454c8fc8fe59a96f2fdcb360bfba12c33
Timestamp: 1716530374 Timestamp [UCT]: 2024-05-24 05:59:34 Age [y:d:h:m:s]: 01:168:15:07:41
Block: 1028798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379107 RingCT/type: yes/0
Extra: 01d0c06838c8048ff4f0679b6beaeb097454c8fc8fe59a96f2fdcb360bfba12c3302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa7ff2be2b74a060feefdf8540efd245bd5a876b0d59086676be1ff1d9167692 0.600000000000 1496795 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": 1028808, "vin": [ { "gen": { "height": 1028798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa7ff2be2b74a060feefdf8540efd245bd5a876b0d59086676be1ff1d9167692" } } ], "extra": [ 1, 208, 192, 104, 56, 200, 4, 143, 244, 240, 103, 155, 107, 234, 235, 9, 116, 84, 200, 252, 143, 229, 154, 150, 242, 253, 203, 54, 11, 251, 161, 44, 51, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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