Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fab6f4828baac04b34f8c9807beccabb585787513ff31e03452fe7f2a1a5e84

Tx prefix hash: 8ccca1437edd7fe931ef63bc7a0ca82b50066e7e8b756bb74090a0e4bc7e52d5
Tx public key: b08bc1d7c5b060ce46aa3b77fa53a66f1a015d45e949bd46d9323e1fc6638aad
Timestamp: 1725612169 Timestamp [UCT]: 2024-09-06 08:42:49 Age [y:d:h:m:s]: 00:190:14:40:58
Block: 1104087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136088 RingCT/type: yes/0
Extra: 01b08bc1d7c5b060ce46aa3b77fa53a66f1a015d45e949bd46d9323e1fc6638aad021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 275899c2d479d9d91dc146638f961a68e8a8aca4d119f814d54fb9b2c86d3ca8 0.600000000000 1581150 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": 1104097, "vin": [ { "gen": { "height": 1104087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "275899c2d479d9d91dc146638f961a68e8a8aca4d119f814d54fb9b2c86d3ca8" } } ], "extra": [ 1, 176, 139, 193, 215, 197, 176, 96, 206, 70, 170, 59, 119, 250, 83, 166, 111, 26, 1, 93, 69, 233, 73, 189, 70, 217, 50, 62, 31, 198, 99, 138, 173, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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