Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92cfe7ecd688429c4718ae74fbfd0b31a6ea0639db61864e5861b32f8ba54588

Tx prefix hash: 6e301ac7132656bb2857adcd4854ce0203e2bef6826f1f969e6d9f708b3fd234
Tx public key: a51f80f61f5c6c806874991243b8706caf37a8028c0ab513e35a400ae2136ae7
Timestamp: 1725855638 Timestamp [UCT]: 2024-09-09 04:20:38 Age [y:d:h:m:s]: 00:194:03:51:52
Block: 1106103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138597 RingCT/type: yes/0
Extra: 01a51f80f61f5c6c806874991243b8706caf37a8028c0ab513e35a400ae2136ae7021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9a4e031515d1264b381f3711bd8e4e07fa4ef529427f81752e66f5d667b5e4d 0.600000000000 1583674 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": 1106113, "vin": [ { "gen": { "height": 1106103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9a4e031515d1264b381f3711bd8e4e07fa4ef529427f81752e66f5d667b5e4d" } } ], "extra": [ 1, 165, 31, 128, 246, 31, 92, 108, 128, 104, 116, 153, 18, 67, 184, 112, 108, 175, 55, 168, 2, 140, 10, 181, 19, 227, 90, 64, 10, 226, 19, 106, 231, 2, 17, 0, 0, 0, 5, 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