Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36061b429deb07292b2ca4fa8ad6e06cb44c6e6182b09891b84b33497d5a91a4

Tx prefix hash: b81f718a34df62da389eddd2aa7e1d1353d783d44c00d33d2b6ebbb963126054
Tx public key: 534f7fb4dde98774dcb9961986ffb66a2386f5202a25ba49fce021e9a939eaea
Timestamp: 1711954524 Timestamp [UCT]: 2024-04-01 06:55:24 Age [y:d:h:m:s]: 00:329:05:19:46
Block: 990820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235390 RingCT/type: yes/0
Extra: 01534f7fb4dde98774dcb9961986ffb66a2386f5202a25ba49fce021e9a939eaea02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c013a157229de7e39053bcae5f7f9f78fa30c00a33c803b8e790afaaa4a02a1a 0.600000000000 1451150 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": 990830, "vin": [ { "gen": { "height": 990820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c013a157229de7e39053bcae5f7f9f78fa30c00a33c803b8e790afaaa4a02a1a" } } ], "extra": [ 1, 83, 79, 127, 180, 221, 233, 135, 116, 220, 185, 150, 25, 134, 255, 182, 106, 35, 134, 245, 32, 42, 37, 186, 73, 252, 224, 33, 233, 169, 57, 234, 234, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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