Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7b1505fc456eb9353b3d324c490ff37fb601dfcc2ecdf674019ac0573d86707

Tx prefix hash: ad2eaf188d461d7b0f3e2df817a9eef140770a75e1bec6e050308fc1ad0ab9d3
Tx public key: 3b14c2ffe123f9ef01d2e5cbff4243e390fbe29b85f96fd025e2bdd25e172b4d
Timestamp: 1709154359 Timestamp [UCT]: 2024-02-28 21:05:59 Age [y:d:h:m:s]: 01:047:20:29:34
Block: 967646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295211 RingCT/type: yes/0
Extra: 013b14c2ffe123f9ef01d2e5cbff4243e390fbe29b85f96fd025e2bdd25e172b4d0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c26e0c8f2276c6e59957e143dde32dddf342791cee09275eb8cf9e1cedeb1301 0.600000000000 1427429 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": 967656, "vin": [ { "gen": { "height": 967646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c26e0c8f2276c6e59957e143dde32dddf342791cee09275eb8cf9e1cedeb1301" } } ], "extra": [ 1, 59, 20, 194, 255, 225, 35, 249, 239, 1, 210, 229, 203, 255, 66, 67, 227, 144, 251, 226, 155, 133, 249, 111, 208, 37, 226, 189, 210, 94, 23, 43, 77, 2, 17, 0, 0, 0, 8, 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