Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3c9d52f778bd90de7f856071d4437c948dc64f3726d449ad9d4b95b010b6ff8

Tx prefix hash: 40c576096cfd935f86fe51cbd15feaf0a26ccf21587e8b3ab6a447f9ec258ad7
Tx public key: d756d5d99c174880e1096222de1cc6378f90e99dfe9f2ca81f6c07e0396f4ae1
Timestamp: 1725148762 Timestamp [UCT]: 2024-08-31 23:59:22 Age [y:d:h:m:s]: 00:244:09:59:36
Block: 1100236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174559 RingCT/type: yes/0
Extra: 01d756d5d99c174880e1096222de1cc6378f90e99dfe9f2ca81f6c07e0396f4ae102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b12bb6df79247aca2f499af7b97068b21195e581138a51c9286d0bc4b2e1dc81 0.600000000000 1576211 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": 1100246, "vin": [ { "gen": { "height": 1100236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b12bb6df79247aca2f499af7b97068b21195e581138a51c9286d0bc4b2e1dc81" } } ], "extra": [ 1, 215, 86, 213, 217, 156, 23, 72, 128, 225, 9, 98, 34, 222, 28, 198, 55, 143, 144, 233, 157, 254, 159, 44, 168, 31, 108, 7, 224, 57, 111, 74, 225, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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