Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c72bccdaef403e8f4b4a08f265f550faf797798bc29bdf58a366d4009b890fb

Tx prefix hash: 055ab18a1ee3a76744a512d06e6390f0b128a98430185759cbe7815661dd5a22
Tx public key: f7806ec1f825bd09b088d09d09e1e789885171b0d567d342aca46c3ebdc3b00f
Timestamp: 1726409595 Timestamp [UCT]: 2024-09-15 14:13:15 Age [y:d:h:m:s]: 00:076:15:52:01
Block: 1110694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54820 RingCT/type: yes/0
Extra: 01f7806ec1f825bd09b088d09d09e1e789885171b0d567d342aca46c3ebdc3b00f021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 870d0f36b3578ef283f81084b0f414727b4673ff8b5e18a4c68e713a2cbf2ef4 0.600000000000 1589389 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": 1110704, "vin": [ { "gen": { "height": 1110694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "870d0f36b3578ef283f81084b0f414727b4673ff8b5e18a4c68e713a2cbf2ef4" } } ], "extra": [ 1, 247, 128, 110, 193, 248, 37, 189, 9, 176, 136, 208, 157, 9, 225, 231, 137, 136, 81, 113, 176, 213, 103, 211, 66, 172, 164, 108, 62, 189, 195, 176, 15, 2, 17, 0, 0, 0, 3, 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