Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f7415a8aee8a7106c3e2e8e523c59bcbb988d09c030e0c88607ff038ccc415d

Tx prefix hash: d8039a7c654553c71278467030095198c0d3378dc17fadbdd1444860c334f23b
Tx public key: f26fe10c4c8fa244f8ccaf0af61e3f707055ecf9a2f9443ed9d97b21f5c2efd8
Timestamp: 1729121571 Timestamp [UCT]: 2024-10-16 23:32:51 Age [y:d:h:m:s]: 01:049:09:55:20
Block: 1133180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293720 RingCT/type: yes/0
Extra: 01f26fe10c4c8fa244f8ccaf0af61e3f707055ecf9a2f9443ed9d97b21f5c2efd80211000000043cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5990520c5bac643782e47b618bd5c43770b676a6ff9502b2db4f6641cf44a66 0.600000000000 1616251 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": 1133190, "vin": [ { "gen": { "height": 1133180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5990520c5bac643782e47b618bd5c43770b676a6ff9502b2db4f6641cf44a66" } } ], "extra": [ 1, 242, 111, 225, 12, 76, 143, 162, 68, 248, 204, 175, 10, 246, 30, 63, 112, 112, 85, 236, 249, 162, 249, 68, 62, 217, 217, 123, 33, 245, 194, 239, 216, 2, 17, 0, 0, 0, 4, 60, 208, 252, 6, 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