Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cc64fd6923ca46a4f6c6b92e0e91eadc2eab298fa78aefbdf3b5b813c9d693e

Tx prefix hash: 2280d45c3626317b08afe61a5db1ce7ba4972b1eca7b9e08666a342cd891cf8b
Tx public key: 37ce113413f0d90b3b2de718c84cdb5aa2834e15774cfcb18ce0a8c57f518bdd
Timestamp: 1709478951 Timestamp [UCT]: 2024-03-03 15:15:51 Age [y:d:h:m:s]: 01:104:12:24:15
Block: 970334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335648 RingCT/type: yes/0
Extra: 0137ce113413f0d90b3b2de718c84cdb5aa2834e15774cfcb18ce0a8c57f518bdd0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8933a3e590f575ff215a8aac3e23f5c95c2071eca9f8de4738230266b2d8e1b1 0.600000000000 1430185 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": 970344, "vin": [ { "gen": { "height": 970334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8933a3e590f575ff215a8aac3e23f5c95c2071eca9f8de4738230266b2d8e1b1" } } ], "extra": [ 1, 55, 206, 17, 52, 19, 240, 217, 11, 59, 45, 231, 24, 200, 76, 219, 90, 162, 131, 78, 21, 119, 76, 252, 177, 140, 224, 168, 197, 127, 81, 139, 221, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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