Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7c1b7e258105031bda46a939b598778199721e2bfe37c4ec16adb7dc33ed666

Tx prefix hash: dd6d073941e31cf177a9a260c58ee25f9abc6e7ad86677791c4f89b4905b8843
Tx public key: bb03d3bec26692d2bf8f5ad58af7e2dc1b69f08d7d77083137782d0d53a6ed7e
Timestamp: 1729068288 Timestamp [UCT]: 2024-10-16 08:44:48 Age [y:d:h:m:s]: 00:000:10:03:03
Block: 1132747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286 RingCT/type: yes/0
Extra: 01bb03d3bec26692d2bf8f5ad58af7e2dc1b69f08d7d77083137782d0d53a6ed7e0211000000053cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37d180a163747dcb7f797639661e78fc64a8a0023d3f290491c992b9639bdc5d 0.600000000000 1615732 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": 1132757, "vin": [ { "gen": { "height": 1132747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37d180a163747dcb7f797639661e78fc64a8a0023d3f290491c992b9639bdc5d" } } ], "extra": [ 1, 187, 3, 211, 190, 194, 102, 146, 210, 191, 143, 90, 213, 138, 247, 226, 220, 27, 105, 240, 141, 125, 119, 8, 49, 55, 120, 45, 13, 83, 166, 237, 126, 2, 17, 0, 0, 0, 5, 60, 208, 252, 6, 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