Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdb34c5efc97e6e3e6e785f215d50489c06b1a0a48ea81a116490e96e496e5a9

Tx prefix hash: 337b9a8caac4dd4a5876b4f15db9af78dd78025bd350627c3c14e0a8a4df151a
Tx public key: 20a40f2df08d250a59bf8711612369831f4894814a6c4289b3cc697287e67a6d
Timestamp: 1729670755 Timestamp [UCT]: 2024-10-23 08:05:55 Age [y:d:h:m:s]: 00:142:04:24:36
Block: 1137699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101431 RingCT/type: yes/0
Extra: 0120a40f2df08d250a59bf8711612369831f4894814a6c4289b3cc697287e67a6d021100000001dcb45f33000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92d8b311c9da3d0c9ec27b15bac9703dab2a32464e8e39bbef014fa4366f059d 0.600000000000 1621238 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": 1137709, "vin": [ { "gen": { "height": 1137699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92d8b311c9da3d0c9ec27b15bac9703dab2a32464e8e39bbef014fa4366f059d" } } ], "extra": [ 1, 32, 164, 15, 45, 240, 141, 37, 10, 89, 191, 135, 17, 97, 35, 105, 131, 31, 72, 148, 129, 74, 108, 66, 137, 179, 204, 105, 114, 135, 230, 122, 109, 2, 17, 0, 0, 0, 1, 220, 180, 95, 51, 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