Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1789431ca65c45c375df39e263f23bc588dac7cd9a335214267855e99a8d6ba

Tx prefix hash: b1fd83b6d8497e7b7b79ef1d0c6e47094237c0ce46bd92b1bd4948c24060fbca
Tx public key: cee54f33bdbab4f430e90f5a92e0a3ae8c0e3a3a1e9947bb287e261d33bc6524
Timestamp: 1721632367 Timestamp [UCT]: 2024-07-22 07:12:47 Age [y:d:h:m:s]: 01:108:12:23:37
Block: 1071081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336063 RingCT/type: yes/0
Extra: 01cee54f33bdbab4f430e90f5a92e0a3ae8c0e3a3a1e9947bb287e261d33bc65240211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d430b16ab459e7e5c2132ffb1389736bd9d5a16775ab8802ea3d4aebcc76acb1 0.600000000000 1543172 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": 1071091, "vin": [ { "gen": { "height": 1071081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d430b16ab459e7e5c2132ffb1389736bd9d5a16775ab8802ea3d4aebcc76acb1" } } ], "extra": [ 1, 206, 229, 79, 51, 189, 186, 180, 244, 48, 233, 15, 90, 146, 224, 163, 174, 140, 14, 58, 58, 30, 153, 71, 187, 40, 126, 38, 29, 51, 188, 101, 36, 2, 17, 0, 0, 0, 1, 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