Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1aca43aa02d868a88f526de97e42fa6d4cb1f3d62e10e6a8b72cd63298bbbec

Tx prefix hash: 9094bd1032d7810f16b5a3b6596bea5998730f86cd30dbf51fc73a30b2f9a58f
Tx public key: 226016387edde878b37a78a414caf6b70315a8c9fc50a814efdc075ebe4da3c7
Timestamp: 1729072322 Timestamp [UCT]: 2024-10-16 09:52:02 Age [y:d:h:m:s]: 00:039:08:59:30
Block: 1132783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28090 RingCT/type: yes/0
Extra: 01226016387edde878b37a78a414caf6b70315a8c9fc50a814efdc075ebe4da3c70211000000183cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9222d0048351d0b73293cd27cc83c71eff3ebdcf875440a3e5bbd1f41e615b4 0.600000000000 1615780 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": 1132793, "vin": [ { "gen": { "height": 1132783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9222d0048351d0b73293cd27cc83c71eff3ebdcf875440a3e5bbd1f41e615b4" } } ], "extra": [ 1, 34, 96, 22, 56, 126, 221, 232, 120, 179, 122, 120, 164, 20, 202, 246, 183, 3, 21, 168, 201, 252, 80, 168, 20, 239, 220, 7, 94, 190, 77, 163, 199, 2, 17, 0, 0, 0, 24, 60, 208, 252, 6, 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