Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5b3bd3b23a16dfafc4849cfb1c14c854c9a9eced51313948f4ebbe0094a758b

Tx prefix hash: c87c58aea5f4bd28fbc83c624ce2f24f877a10a9854818df404b75b9798636e4
Tx public key: 3f410c3bd5cedbb2d17ef30752ef845177007ac25a4fa6c177858f9c38f53cb2
Timestamp: 1719724662 Timestamp [UCT]: 2024-06-30 05:17:42 Age [y:d:h:m:s]: 00:285:06:52:54
Block: 1055265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203869 RingCT/type: yes/0
Extra: 013f410c3bd5cedbb2d17ef30752ef845177007ac25a4fa6c177858f9c38f53cb20211000000020cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 680ddb9a282d421d5f3979acc36decab81a9453e24f7a2c70a2435f4cb2f5466 0.600000000000 1525662 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": 1055275, "vin": [ { "gen": { "height": 1055265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "680ddb9a282d421d5f3979acc36decab81a9453e24f7a2c70a2435f4cb2f5466" } } ], "extra": [ 1, 63, 65, 12, 59, 213, 206, 219, 178, 209, 126, 243, 7, 82, 239, 132, 81, 119, 0, 122, 194, 90, 79, 166, 193, 119, 133, 143, 156, 56, 245, 60, 178, 2, 17, 0, 0, 0, 2, 12, 206, 6, 54, 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