Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d560efff7103526647db6ea5e84a0f7f0403ecfdf1e7ba6123da5557fe930328

Tx prefix hash: a85a0ad0c9784bfd00cd55cf12054cfbca5ccb9a4e667dc249920aab9a884c50
Tx public key: 55bc41cebaa014e380cc9e0b4d2e5a3dcdd01aaaa3d83cff0491a95909882754
Timestamp: 1733771634 Timestamp [UCT]: 2024-12-09 19:13:54 Age [y:d:h:m:s]: 00:188:09:11:45
Block: 1171633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134371 RingCT/type: yes/0
Extra: 0155bc41cebaa014e380cc9e0b4d2e5a3dcdd01aaaa3d83cff0491a959098827540211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9eebe9e765462b2ed9a178df764bc7c3c7a5ab4e1d92c00c26eba3b4c86096a8 0.600000000000 1657414 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": 1171643, "vin": [ { "gen": { "height": 1171633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9eebe9e765462b2ed9a178df764bc7c3c7a5ab4e1d92c00c26eba3b4c86096a8" } } ], "extra": [ 1, 85, 188, 65, 206, 186, 160, 20, 227, 128, 204, 158, 11, 77, 46, 90, 61, 205, 208, 26, 170, 163, 216, 60, 255, 4, 145, 169, 89, 9, 136, 39, 84, 2, 17, 0, 0, 0, 4, 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