Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a16abf8cb3594014220dc4c6b85bfe1a71015497e1c07528e3a726addbe2a072

Tx prefix hash: e4f0fbeca97f246b59f96b039be2d6d76850560d659a6ec6aa384898909fe810
Tx public key: b3dedb5394c65553dadbb696b428b96e5b448c95e47f68232f8b7d241926ecb9
Timestamp: 1723114292 Timestamp [UCT]: 2024-08-08 10:51:32 Age [y:d:h:m:s]: 01:093:05:30:35
Block: 1083375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325108 RingCT/type: yes/0
Extra: 01b3dedb5394c65553dadbb696b428b96e5b448c95e47f68232f8b7d241926ecb9021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cea5f2266c538bc4cc8fb07c3347d992d3068d59e1e3810df9fa0d7b57d4c37c 0.600000000000 1557272 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": 1083385, "vin": [ { "gen": { "height": 1083375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cea5f2266c538bc4cc8fb07c3347d992d3068d59e1e3810df9fa0d7b57d4c37c" } } ], "extra": [ 1, 179, 222, 219, 83, 148, 198, 85, 83, 218, 219, 182, 150, 180, 40, 185, 110, 91, 68, 140, 149, 228, 127, 104, 35, 47, 139, 125, 36, 25, 38, 236, 185, 2, 17, 0, 0, 0, 2, 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