Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f957d2e22043a68ca067cbf27a65c00827edbf6a637712469a84ff902de20f88

Tx prefix hash: ccd4f442e3d8246c0f1abcc8d2b8caf59a2921ce3c063b2838279872c326847f
Tx public key: 0a78840af3c031542dcf9a8943042fcb7afbdeecfd0113d2407c39553b4c4564
Timestamp: 1737946959 Timestamp [UCT]: 2025-01-27 03:02:39 Age [y:d:h:m:s]: 00:143:17:38:50
Block: 1205952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102640 RingCT/type: yes/0
Extra: 010a78840af3c031542dcf9a8943042fcb7afbdeecfd0113d2407c39553b4c45640211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b0d83860ea38f7b5690a0c408d2dfd06315b422cd16bf3d9f0614f3341a9770 0.600000000000 1692651 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": 1205962, "vin": [ { "gen": { "height": 1205952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b0d83860ea38f7b5690a0c408d2dfd06315b422cd16bf3d9f0614f3341a9770" } } ], "extra": [ 1, 10, 120, 132, 10, 243, 192, 49, 84, 45, 207, 154, 137, 67, 4, 47, 203, 122, 251, 222, 236, 253, 1, 19, 210, 64, 124, 57, 85, 59, 76, 69, 100, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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