Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfb8d69884424f8b9c09d64f86c0e56377331911ddc67fd683dd3d413af38cbf

Tx prefix hash: 448ec35300162765a3eddccf6d0f8a4560d4439ce6c89a3b7db6a78dd1fa0755
Tx public key: e56d34316a0def719f5ba1949448bfc2336f84ce8ee24a4c05b025ae1b335a33
Timestamp: 1716787624 Timestamp [UCT]: 2024-05-27 05:27:04 Age [y:d:h:m:s]: 00:304:21:54:46
Block: 1030935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217902 RingCT/type: yes/0
Extra: 01e56d34316a0def719f5ba1949448bfc2336f84ce8ee24a4c05b025ae1b335a330211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b57920882654027b087185c894f1eda82df1a61e81e7cd54c53784a05ba9996 0.600000000000 1499258 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": 1030945, "vin": [ { "gen": { "height": 1030935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b57920882654027b087185c894f1eda82df1a61e81e7cd54c53784a05ba9996" } } ], "extra": [ 1, 229, 109, 52, 49, 106, 13, 239, 113, 159, 91, 161, 148, 148, 72, 191, 194, 51, 111, 132, 206, 142, 226, 74, 76, 5, 176, 37, 174, 27, 51, 90, 51, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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