Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f17a21e9c33df0759a6c92d2be3b0a3ca253788761e5182e4770467204c58d50

Tx prefix hash: 447f3b55ae259c3424485465b1b0a5e3170a1ae010ce8c4abe686573f88d38cb
Tx public key: b0a540d26839de390be9596e73eb4046cf3e79612c83fbac6afb5a076c99a8bc
Timestamp: 1706777663 Timestamp [UCT]: 2024-02-01 08:54:23 Age [y:d:h:m:s]: 01:125:17:26:23
Block: 947916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350973 RingCT/type: yes/0
Extra: 01b0a540d26839de390be9596e73eb4046cf3e79612c83fbac6afb5a076c99a8bc0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e171de6a9a0a060dc64f2eef0ded549984d565c21d04f4ffbefbcf23a8c9a3f 0.600000000000 1406276 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": 947926, "vin": [ { "gen": { "height": 947916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e171de6a9a0a060dc64f2eef0ded549984d565c21d04f4ffbefbcf23a8c9a3f" } } ], "extra": [ 1, 176, 165, 64, 210, 104, 57, 222, 57, 11, 233, 89, 110, 115, 235, 64, 70, 207, 62, 121, 97, 44, 131, 251, 172, 106, 251, 90, 7, 108, 153, 168, 188, 2, 17, 0, 0, 0, 1, 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