Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32cd35a57db87b385d41367c9a1391d2e5114eee0ef4ab86aec7fb4f85f003d2

Tx prefix hash: 6258ef4db60ee32744c9b10d897b672b73b9a3e6034a90be282e69fa7e818d6e
Tx public key: b484e1b76714e0fec7d146469bc7021d785a69fdeb0184d3fa7d833c2f7ac624
Timestamp: 1722192758 Timestamp [UCT]: 2024-07-28 18:52:38 Age [y:d:h:m:s]: 00:238:13:30:47
Block: 1075735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170398 RingCT/type: yes/0
Extra: 01b484e1b76714e0fec7d146469bc7021d785a69fdeb0184d3fa7d833c2f7ac624021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ced1869b68c22d5e8433711f4cbe4dc6bd6b58bbe22046e6b41d1b0f6da5f48 0.600000000000 1548264 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": 1075745, "vin": [ { "gen": { "height": 1075735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ced1869b68c22d5e8433711f4cbe4dc6bd6b58bbe22046e6b41d1b0f6da5f48" } } ], "extra": [ 1, 180, 132, 225, 183, 103, 20, 224, 254, 199, 209, 70, 70, 155, 199, 2, 29, 120, 90, 105, 253, 235, 1, 132, 211, 250, 125, 131, 60, 47, 122, 198, 36, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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