Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5794a2c599547ee7076ce579637d216330d8bcb79596364c5a13a50f84cda94a

Tx prefix hash: b206b2916dd2d9b2e2a23c6f5b480c9df5bba7654ca913fbdad1d6f093b260b1
Tx public key: ef1c3583a848e096cbdeff7e519783cae83ea1530b003890a204a97e37d8066c
Timestamp: 1725084769 Timestamp [UCT]: 2024-08-31 06:12:49 Age [y:d:h:m:s]: 00:244:12:08:29
Block: 1099710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174621 RingCT/type: yes/0
Extra: 01ef1c3583a848e096cbdeff7e519783cae83ea1530b003890a204a97e37d8066c021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f4e1a1c6ba46714eec8ecf7fe5dadb6208523017db852f4c710512832a2eadc 0.600000000000 1575677 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": 1099720, "vin": [ { "gen": { "height": 1099710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f4e1a1c6ba46714eec8ecf7fe5dadb6208523017db852f4c710512832a2eadc" } } ], "extra": [ 1, 239, 28, 53, 131, 168, 72, 224, 150, 203, 222, 255, 126, 81, 151, 131, 202, 232, 62, 161, 83, 11, 0, 56, 144, 162, 4, 169, 126, 55, 216, 6, 108, 2, 17, 0, 0, 0, 8, 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