Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d012e6cf041bfa1663cf6c133c1c90be4f3dc560441fd761fbb86c56c2147fc3

Tx prefix hash: 9942b5f291dc70e5f87f4f62b9f41c6a84a4a86aeff7e682b4d384c2261f0149
Tx public key: 7e67d0cf88d9ab25c9e910e60dd45a715d9256454c485cde96d0f1e1c4b8cc8c
Timestamp: 1736869287 Timestamp [UCT]: 2025-01-14 15:41:27 Age [y:d:h:m:s]: 00:154:15:48:52
Block: 1197262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110237 RingCT/type: yes/0
Extra: 017e67d0cf88d9ab25c9e910e60dd45a715d9256454c485cde96d0f1e1c4b8cc8c0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffc575d6e4f653929b6b61d89975ee1929045d2ba5e6577b46088218f93f145f 0.600000000000 1683869 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": 1197272, "vin": [ { "gen": { "height": 1197262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffc575d6e4f653929b6b61d89975ee1929045d2ba5e6577b46088218f93f145f" } } ], "extra": [ 1, 126, 103, 208, 207, 136, 217, 171, 37, 201, 233, 16, 230, 13, 212, 90, 113, 93, 146, 86, 69, 76, 72, 92, 222, 150, 208, 241, 225, 196, 184, 204, 140, 2, 17, 0, 0, 0, 7, 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