Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e81bf0856f3f6619959d776828333032d2002ad96648ecf4f52bf2eca3326d48

Tx prefix hash: d87e8c307346afb00602dc2c8ee046b5a6557a46aa9cc49a4581d75131595a67
Tx public key: b4e8db9cfa83b00b9a02a8fff410024d3e14f9cea4b038013c7d123ece405bc5
Timestamp: 1712271783 Timestamp [UCT]: 2024-04-04 23:03:03 Age [y:d:h:m:s]: 01:054:05:10:04
Block: 993471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299762 RingCT/type: yes/0
Extra: 01b4e8db9cfa83b00b9a02a8fff410024d3e14f9cea4b038013c7d123ece405bc50211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02d47b4ecaf0b6b163e814b64372e3569e8eb785e4cfbe581ff9bf8eb0f89b27 0.600000000000 1453857 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": 993481, "vin": [ { "gen": { "height": 993471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02d47b4ecaf0b6b163e814b64372e3569e8eb785e4cfbe581ff9bf8eb0f89b27" } } ], "extra": [ 1, 180, 232, 219, 156, 250, 131, 176, 11, 154, 2, 168, 255, 244, 16, 2, 77, 62, 20, 249, 206, 164, 176, 56, 1, 60, 125, 18, 62, 206, 64, 91, 197, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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