Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3a72454fc67a59170b1486bc1269257d1517daba3e15a5eaab6ef9a65486282

Tx prefix hash: 924cd52756aee7993c5a6602481cb0f3a42bcdab7605d0f5db5d514f4d7cda5e
Tx public key: 71be33b41f3c0897044373cc8535323a4d4343b2cc1def3e5f30604ac334b0e4
Timestamp: 1701208992 Timestamp [UCT]: 2023-11-28 22:03:12 Age [y:d:h:m:s]: 01:132:08:59:18
Block: 901779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355758 RingCT/type: yes/0
Extra: 0171be33b41f3c0897044373cc8535323a4d4343b2cc1def3e5f30604ac334b0e402110000000b33af99f4000000000000000000

1 output(s) for total of 0.631003557000 dcy

stealth address amount amount idx
00: 4c50e17427d40e9f8ed076b3a823bd40022b359881aaebca96dce5daeb2888f7 0.631003557000 1358370 of 0

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": 901789, "vin": [ { "gen": { "height": 901779 } } ], "vout": [ { "amount": 631003557, "target": { "key": "4c50e17427d40e9f8ed076b3a823bd40022b359881aaebca96dce5daeb2888f7" } } ], "extra": [ 1, 113, 190, 51, 180, 31, 60, 8, 151, 4, 67, 115, 204, 133, 53, 50, 58, 77, 67, 67, 178, 204, 29, 239, 62, 95, 48, 96, 74, 195, 52, 176, 228, 2, 17, 0, 0, 0, 11, 51, 175, 153, 244, 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