Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 238efdfb84d6a630adf2ac088004a89dd164a03a72c1a24c084b692002d10ec9

Tx prefix hash: 477ecd148b744143fda0a809eef5188a42a3e3e4400b055d4a6200cbca09dc2a
Tx public key: 800d355b82f10f40a1673cd4a1919414edc71d88e0ade5f6e6276d4ada172f0f
Timestamp: 1764321068 Timestamp [UCT]: 2025-11-28 09:11:08 Age [y:d:h:m:s]: 00:025:18:28:54
Block: 1421872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18443 RingCT/type: yes/0
Extra: 01800d355b82f10f40a1673cd4a1919414edc71d88e0ade5f6e6276d4ada172f0f0211000000024e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ffaf97c19101a6d438e9d9691fd8e5ae9160d57c414a84b00aa8339670d4dcb 0.600000000000 1910433 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": 1421882, "vin": [ { "gen": { "height": 1421872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ffaf97c19101a6d438e9d9691fd8e5ae9160d57c414a84b00aa8339670d4dcb" } } ], "extra": [ 1, 128, 13, 53, 91, 130, 241, 15, 64, 161, 103, 60, 212, 161, 145, 148, 20, 237, 199, 29, 136, 224, 173, 229, 246, 230, 39, 109, 74, 218, 23, 47, 15, 2, 17, 0, 0, 0, 2, 78, 123, 252, 9, 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