Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aff64cde36de50c03fd90c7d252509e4485584b2814a3b21bf093ea9f98f1585

Tx prefix hash: 72a5dea507a20a3be3cda53d7ff631ef5b09f3170b948729bee21bd4cf09a601
Tx public key: b995ffbd45bcc9a1f8e44b663ae768da02127562a9a6a6ffd985e6042fd759fc
Timestamp: 1706542841 Timestamp [UCT]: 2024-01-29 15:40:41 Age [y:d:h:m:s]: 01:139:19:35:22
Block: 945968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360951 RingCT/type: yes/0
Extra: 01b995ffbd45bcc9a1f8e44b663ae768da02127562a9a6a6ffd985e6042fd759fc02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94e94fdee601b9a683c854a452950dfd827c55c06a976c433462804cf7ecaa0b 0.600000000000 1404298 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": 945978, "vin": [ { "gen": { "height": 945968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94e94fdee601b9a683c854a452950dfd827c55c06a976c433462804cf7ecaa0b" } } ], "extra": [ 1, 185, 149, 255, 189, 69, 188, 201, 161, 248, 228, 75, 102, 58, 231, 104, 218, 2, 18, 117, 98, 169, 166, 166, 255, 217, 133, 230, 4, 47, 215, 89, 252, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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