Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 954934f7675b84835f232f78f4921043c3fb5dcc37fea325e628bcd675f19826

Tx prefix hash: f7cee8fd1a34a58c0869bb62c91ffdddeaf041d1dd2e45b8a3be8251fe0efe5f
Tx public key: 4289dc87b6107231d61aebbfd5cb1dddb20d8fb0f7060a517dc4689551359808
Timestamp: 1729703371 Timestamp [UCT]: 2024-10-23 17:09:31 Age [y:d:h:m:s]: 00:167:03:00:38
Block: 1137967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119239 RingCT/type: yes/0
Extra: 014289dc87b6107231d61aebbfd5cb1dddb20d8fb0f7060a517dc46895513598080211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40eff1b3aa3266aaa24e5b55d7cb19cc5075e0b878ecbb4d4ee91789b55eb306 0.600000000000 1621560 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": 1137977, "vin": [ { "gen": { "height": 1137967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40eff1b3aa3266aaa24e5b55d7cb19cc5075e0b878ecbb4d4ee91789b55eb306" } } ], "extra": [ 1, 66, 137, 220, 135, 182, 16, 114, 49, 214, 26, 235, 191, 213, 203, 29, 221, 178, 13, 143, 176, 247, 6, 10, 81, 125, 196, 104, 149, 81, 53, 152, 8, 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